jupiter/src/storage/init.rs:54

• The setup_sql function (and its imports) is commented out but still present. Remove unused code or fully restore it to keep the file clean and ensure initialization logic remains correct.

/// create table from .sql file

jupiter/sqlite_20241204_init.sql:1

• This file is now empty except for a relative path reference. Either restore valid SQL or remove the file reference entirely to avoid initialization errors.

../sql/sqlite/sqlite_20241204_init.sql

docs/development.md:49

• Documentation still outlines manual SQL updates and filename conventions that no longer apply after switching to SeaORM migrations. Update this section to reflect the new migration workflow.

Whenever making any updates to the SQL content

mono/src/api/issue/issue_router.rs:35

• Several new Issue endpoints have been added without accompanying tests. Add unit or integration tests to cover fetch_issue_list, new_issue, and other handlers to ensure reliability.

async fn fetch_issue_list

mono/src/api/mr/mr_router.rs:64

• You’ve commented out permission checks and hardcoded user values (0, "admin"), effectively disabling auth. Restore proper LoginUser extraction and permission checks to prevent unauthorized access.

.reopen_mr(mr.into(), 0, "admin")

mono/src/api/api_router.rs:83

• Changing /create-file from GET to POST may break existing clients and docs. Ensure you update documentation and client-side code to match the new method.

post,

jupiter/src/storage/mono_storage.rs:92

• Commenting out the IsMr filter means you’ll fetch all refs (including merge requests), which can degrade performance and return unintended data. Re-enable or adjust this filter.

// .filter(mega_refs::Column::IsMr.eq(false))

mono/src/api/issue/issue_router.rs:14

• [nitpick] Importing SaveCommentRequest from the mr module in the issue router creates cross-module coupling. Consider moving shared types to a common module or defining a dedicated type in the issue API.

use crate::api::mr::{SaveCommentRequest};